Skip to content

feat(slab): using slab new routes to handle async tasks#70

Merged
soonum merged 1 commit intomainfrom
dt/feat/support_new_tasks
Jan 16, 2026
Merged

feat(slab): using slab new routes to handle async tasks#70
soonum merged 1 commit intomainfrom
dt/feat/support_new_tasks

Conversation

@soonum
Copy link
Contributor

@soonum soonum commented Dec 8, 2025

This ensure to wait for individual asynchronous tasks since there are GitHub related operations and backend providers ones.


This change is Reviewable

@soonum soonum requested a review from IceTDrinker December 8, 2025 14:21
@soonum soonum self-assigned this Dec 8, 2025
@soonum soonum added the enhancement New feature or request label Dec 8, 2025
@soonum soonum force-pushed the dt/feat/support_new_tasks branch 2 times, most recently from d2c3496 to ef7acd0 Compare December 9, 2025 16:50
@soonum soonum force-pushed the dt/feat/support_new_tasks branch from ef7acd0 to 1641b21 Compare January 14, 2026 08:30
@soonum soonum requested a review from IceTDrinker January 14, 2026 09:24
} catch (error) {
core.info(`Clean up after error, stop ${provider} instance`)
await slab.stopInstanceRequest(startInstanceResponse.runner_name)
await slab.stopInstanceRequest(runnerName)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

runner name could be empty here maybe ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added an early return to avoid falling in this case.
In fact if Github operation fails in this function, the instance would not be started.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While writting my last message I think we can go back for the previous implem.
I've to check if the instance record is not updated in case of Github error.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I somewhat rolled back the implementation for start. Since it can be safely relaunched without having zombies.

@soonum soonum force-pushed the dt/feat/support_new_tasks branch from 1641b21 to b716cc3 Compare January 15, 2026 16:20
@soonum soonum requested a review from IceTDrinker January 15, 2026 16:20
Copy link
Member

@IceTDrinker IceTDrinker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks !

@IceTDrinker reviewed 4 files and all commit messages, and made 1 comment.
Reviewable status: all files reviewed, 5 unresolved discussions (waiting on @soonum).

This ensures to wait for individual asynchronous tasks since there
are GitHub-related operations and backend providers ones.
@soonum soonum force-pushed the dt/feat/support_new_tasks branch from b716cc3 to fd7e64f Compare January 15, 2026 16:47
@soonum soonum requested a review from IceTDrinker January 15, 2026 16:49
Copy link
Member

@IceTDrinker IceTDrinker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@IceTDrinker reviewed 2 files and all commit messages.
Reviewable status: all files reviewed, 5 unresolved discussions (waiting on @soonum).

@soonum soonum merged commit c4e972d into main Jan 16, 2026
27 checks passed
@soonum soonum deleted the dt/feat/support_new_tasks branch January 16, 2026 10:30
@soonum
Copy link
Contributor Author

soonum commented Jan 16, 2026

🎉 This PR is included in version 1.5.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request released

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants